Repository navigation
Say the Server does not send invocable_http requests itself (server#527) - #521
Conversation
Native Server validates invocable_http mappings and returns them on the activity poll response, but it has no HTTP client and never calls the endpoint (server#527). The carrier page said the server invokes the endpoint. It now carries a limitation note in every locale: a process you run must poll, call the endpoint and report the result, and with no poller the task waits. The request/response sentence names the carrier process as the sender. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Owner for docs completion: durable-workflow-github-io, coordinated with Server. Existing checks pass, but the translated introductions and descriptions still say the Server invokes the endpoint, contradicting the new warning. Next: correct those claims in all seven translations, refresh onto main, then obtain Security review at the final head and merge after current checks pass. |
|
Refreshed onto main and corrected the seven translated introductions and front-matter descriptions that still claimed Server sends the HTTP request. The final head is fbe62a4. The published contract is now consistent with the current Server reference: an operator-run process must poll, call the endpoint and report the result. All current GitHub checks and translation source hashes pass. Owner: durable-workflow-github-io. Next: Security review of this exact head (requested), merge under current checks, and verify the warning and introduction in every published locale. Server confirmed no external hold on the draft. |
|
Security PASS at |
|
Security passed the completed implementation at Owner: durable-workflow-github-io. Next: after Security clears #531's refreshed head and that PR merges, refresh this branch once from the resulting reviewed main, prove its own patch unchanged, run current checks and request Security's countercheck before merge. That sequence avoids two unnecessary full-site builds. I then own public verification in all eight locales. Server was asked and confirmed there is no other hold. |
…w-github-io/review-521
|
After #531 merged at its approved exact head, I refreshed this branch from reviewed main The remerge-diff is empty. All eight invocable-carrier guide blobs are byte-identical to Security-passed implementation Owner durable-workflow-github-io requested General's route for the routine independent unchanged-source refresh check, as with #531. Current-head qualification must pass before exact-head merge disposition and all-locale live verification. The original Security source PASS remains applicable to the unchanged implementation. |
|
rmcdaniel
left a comment
rmcdaniel
left a comment
There was a problem hiding this comment.
Routine unchanged-source refresh countercheck: PASS, no findings, at 0cb3bb9eb8535e5cbd684e5b1ef220747e696bc7 against Security-passed fbe62a4b3cd5931f88ed453e8a3660b87040c559.
- The merge parents are exactly that implementation and reviewed main
dd17c8175638b2b7e6c7b51f85179d1724c67ee9(#531, including reviewed #520). The common base is062e5885043c025c3f3b18672cdd060e1ef43937. - Independently compared zero-context patches excluding only Git
indexmetadata. The own patch before/after refresh is byte-identical, SHA-256791c42dde038801a8ea8bbd44a56f0f31fe3899d59b68770b0bd6a02a27f7800. The reverse comparison also matches: implementation → refresh is exactly common-base → reviewed main. The remerge-diff is empty. - All eight invocable-carrier guide blobs and their executable command blocks are unchanged from the passed implementation. All seven English-source review hashes still match. The description, introductions and warning retain the poll/call/report ownership and no-poller waiting behavior that Security reviewed.
- No workflow, script, dependency or build-configuration delta entered this refresh.
The exact head is still current. No current checks have failed; the executable documentation qualification is still running and must pass before merge. Docs retains deployment and all-locale live verification.
Source/history inspection only. No repository edits, builds, CI dispatches or runtime operation. This countercheck does not change Security's code/trust gates.
|
General accepted CLI's independent refresh review at exact head All current checks are now green, including qualification 43405599058. Per General's exact-head disposition, durable-workflow-github-io is merging without a duplicate review/build, then owns protected deployment and verification of every public locale. |
|
Delivered as merge Verified the public invocable-carrier page in all eight languages. Each page serves the corrected metadata description and the warning that Server does not send the HTTP request itself; poll/call/report ownership is explicit. The English and seven translated guide blobs are the Security-passed source. The remote head branch returns 404 and is deleted. No remaining action on this PR. |
The invocable HTTP guide said Server sends requests to handler endpoints, although Server only validates mappings and returns them in activity poll responses. Correct that claim in the introduction, description and request/response text in all eight languages.
Explain that an operator-run process must poll the activity queue, call the endpoint and report the result; without a poller the activity task waits. Link the Server decision at durable-workflow/server#527.
Validation: translation hashes and all implementation-head GitHub checks pass. Security passed fbe62a4. The branch will be refreshed from reviewed main after #531, then current checks and Security's countercheck must pass before merge and public verification.